System and method for interactive application preview

ABSTRACT

An interactive demonstration application can be used to test and experience the use of overlay elements (e.g., application add-ons, such as an interactive chat overlay) on a graphical interface (e.g., of a website or a computer application) before fully integrating the overlay elements into the graphical interface. The interactive demonstration application can also be used to demonstrate and update the live settings of a live overlay element used on a live webpage.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 62/064,254, filed Oct. 15, 2014, entitled “SOFTWAREDEMONSTRATION PLATFORM,” which is hereby incorporated by reference inits entirety.

TECHNICAL FIELD

The present disclosure relates to systems and methods for providinginteractive application demonstration and configuration generally, andmore specifically, to interactive demonstration and configuration ofapplication libraries running on websites or in native applications.

SUMMARY

The term embodiment and like terms are intended to refer broadly to allof the subject matter of this disclosure and the claims below.Statements containing these terms should be understood not to limit thesubject matter described herein or to limit the meaning or scope of theclaims below. Embodiments of the present disclosure covered herein aredefined by the claims below, not this summary. This summary is ahigh-level overview of various aspects of the disclosure and introducessome of the concepts that are further described in the DetailedDescription section below. This summary is not intended to identify keyor essential features of the claimed subject matter, nor is it intendedto be used in isolation to determine the scope of the claimed subjectmatter. The subject matter should be understood by reference toappropriate portions of the entire specification of this disclosure, anyor all drawings and each claim.

Certain aspects and features of the present disclosure relate to anapplication that is used to test and experience the use of overlayelements (e.g., application add-ons, such as an interactive chatoverlay) on a graphical interface (e.g., of a website or a computerapplication) before fully integrating the overlay elements into thegraphical interface.

Embodiments of the present disclosure also relate to demonstratingchanges to the appearance, functionality, or appearance andfunctionality of a live overlay element, running on a live website, in ademonstration application. Embodiments also relate to uploading thosechanges to the live website in order to update the live overlay elementwith the changes that were demonstrated in the demonstrationapplication.

In some embodiments, a computer-implemented method may be provided. Thecomputer-implemented method may include displaying, on a computingdevice, a graphical interface corresponding to a live website anddetermining an overlay element. The overlay element may be interactiveand may demonstrate how the overlay element will look and act whenincorporated into the graphical interface corresponding to the livewebsite. The computer-implemented method may also include concurrentlydisplaying the graphical interface with the overlay element. The overlayelement may be incorporated into the graphical interface.

In some embodiments, a system may be provided. The system may includeone or more data processors and a non-transitory computer-readablestorage medium containing instructions which when executed on the one ormore data processors, cause the one or more processors to performoperations. The operations may include displaying a graphical interfacecorresponding to a live website and determining an overlay element. Theoverlay element may be interactive and may demonstrate how the overlayelement will look and act when incorporated into the graphical interfacecorresponding to the live website. The operations may also includeconcurrently displaying the graphical interface with the overlayelement. The overlay element may be incorporated into the graphicalinterface.

In some embodiments, a computer-program product tangibly embodied in anon-transitory machine-readable storage medium may be provided. Thenon-transitory machine-readable storage medium may include instructionsconfigured to cause a data processing apparatus to display a graphicalinterface corresponding to a live website and determine an overlayelement. The overlay element may be interactive and may demonstrate howthe overlay element will look and act when incorporated into thegraphical interface corresponding to the live website. The instructionsmay also cause the data processing apparatus to concurrently display thegraphical interface with the overlay element. The overlay element may beincorporated into the graphical interface.

In some embodiments, a method, system, or computer-program product forperforming actions may be provided, and may include displaying, on acomputing device, a graphical representation of a native application anddetermining an overlay element. In some examples, the overlay elementmay be interactive and may demonstrate how the overlay element will lookand act when incorporated into the native application. The method,system, or computer-program product may also include concurrentlydisplaying the graphical representation with the overlay element. Theoverlay element may be incorporated into the graphical representation.

In some embodiments, a method, system, or computer-program product forperforming actions may be provided, and may include displaying, on acomputing device, a graphical interface of a live native applicationrunning on the computing device and determining an overlay element. Insome examples, the overlay element may be interactive and maydemonstrate how the overlay element will look and act when incorporatedinto the live native application. The method, system, orcomputer-program product may also include concurrently displaying thegraphical interface with the overlay element. The overlay element may beincorporated into the graphical interface.

In some embodiments, a computer-implemented method may be provided. Thecomputer-implemented method may include loading, at a computing device,a demonstration application, accessing a live webpage using thedemonstration application, and simultaneously displaying an overlayelement in addition to the live webpage. Accessing the live webpage mayinclude running the webpage on the computing device. Thecomputer-implemented method may include accessing settings informationfrom a server. In some examples, the settings information may control anappearance or functionality of the overlay element. Thecomputer-implemented method may also include presenting configurablesettings and updating the settings information with the configurablesettings. For example, the configurable settings may include settingsthat control the appearance or functionality of the overlay element.

In some embodiments, a computer-implemented method may be provided. Thecomputer-implemented method may include loading, at a computing device,a demonstration application and accessing a live website using thedemonstration application. Accessing the live website may includerunning the live website on the computing device. Thecomputer-implemented method may also include displaying a graphicalinterface corresponding to the live website. The graphical interface mayinclude code to enable an overlay element. The overlay element may besimultaneously displayed over the graphical interface. In addition, thecomputer-implemented method may include presenting configurable settingsof the overlay element and updating the code to enable the overlayelement with the configurable settings.

In some embodiments, a computer-implemented method may be provided. Thecomputer-implemented method may include loading, at a computing device,a demonstration application, displaying a prompt using the demonstrationapplication, receiving a response to the prompt, and accessing a livewebsite using the response to the prompt. For example, the prompt mayrequest a live website address. Further, the computer-implemented methodmay include displaying a graphical interface corresponding to the livewebsite and determining an overlay element. In some examples,determining the overlay element may include selecting a version of theoverlay element from amongst a plurality of versions of overlayelements. The overlay element may be interactive and may demonstrate howthe overlay element will look and act when incorporated into thegraphical interface corresponding to the live website. Thecomputer-implemented method may also include concurrently displaying thegraphical interface with the overlay element. For example, the overlayelement may be displayed over or in front of the graphical interface. Asanother example, the overlay element can be presented near or around thegraphical interface. In some examples, the overlay element may bevisible after a specific user input, such as a swiping movement.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description and specific examples, whileindicating various embodiments, are intended for purposes ofillustration only and are not intended to necessarily limit the scope ofthe disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The specification makes reference to the following appended figures, inwhich use of like reference numerals in different figures is intended toillustrate like or analogous components.

FIG. 1 shows a block diagram of an embodiment of a network interactionsystem.

FIG. 2 shows a block diagram of another embodiment of a networkinteraction system.

FIGS. 3A-3C show block diagrams of other embodiments of a networkinteraction system that includes a connection management system.

FIG. 4 shows a representation of a protocol-stack mapping of connectioncomponents' operation.

FIG. 5 represents a multi-device communication exchange system accordingto an embodiment.

FIG. 6 shows a block diagram of an embodiment of a connection managementsystem.

FIG. 7 is a block diagram of a demonstration application environmentaccording to one embodiment.

FIG. 8 is a flow chart of a process for demonstrating an application ona computing device.

FIG. 9 is a process for updating a live overlay element from ademonstration application according to one embodiment.

FIG. 10 is a block diagram of a process of demonstrating a chatinterface as an overlay element according to one embodiment.

FIG. 11 illustrates an example of a user device according to oneembodiment.

FIG. 12 illustrates an example of a server, such as a web server or acode server, according to one embodiment.

FIG. 13 is a block diagram of an overlay element demonstration processaccording to one embodiment.

FIG. 14 is a block diagram of an overlay element updating process basedon the overlay element demonstration process of FIG. 13 according to oneembodiment.

FIG. 15 is a depiction of a selection screen displayable on a computingdevice according to one embodiment.

FIG. 16 is a depiction of a URL entry screen displayable on a computingdevice according to one embodiment.

FIG. 17 is a depiction of a web chat initial settings screen displayableon a computing device according to one embodiment.

FIG. 18 is a depiction of a demonstration screen displayable on acomputing device according to one embodiment.

FIG. 19 is a depiction of a demonstration screen with a pre-chat surveywindow displayable on a computing device according to one embodiment.

FIG. 20 is a depiction of a demonstration screen with a name entrywindow displayable on a computing device according to one embodiment.

FIG. 21 is a depiction of a demonstration screen with a chat overlaydisplayable on a computing device according to one embodiment.

FIG. 22 is a depiction of a demonstration screen with a function bardisplayable on a computing device according to one embodiment.

FIG. 23 is a depiction of a settings screen displayable on a computingdevice according to one embodiment.

FIG. 24 is a depiction of a selection screen showing new URL and browserselections displayable on a computing device according to oneembodiment.

FIG. 25 is a depiction of a selection screen displayable on a computingdevice according to one embodiment.

FIG. 26 is a depiction of a native app search screen displayable on acomputing device according to one embodiment.

FIG. 27 is a depiction of a store selection screen displayable on acomputing device according to one embodiment.

FIG. 28 is a depiction of an app selection screen displayable on acomputing device according to one embodiment.

FIG. 29 is a depiction of an app settings screen displayable on acomputing device according to one embodiment.

FIG. 30 is a depiction of an initial settings screen displayable on acomputing device according to one embodiment.

FIG. 31 is a depiction of an initial settings screen displayable on acomputing device according to one embodiment.

FIG. 32 is a depiction of a branding screen displayable on a computingdevice according to one embodiment.

FIG. 33 is a depiction of a demonstration screen displayable on acomputing device according to one embodiment.

FIG. 34 is a depiction of a demonstration screen with a function bardisplayable on a computing device according to one embodiment.

FIG. 35 is a depiction of a demonstration screen with a pre-chat surveywindow displayable on a computing device according to one embodiment.

FIG. 36 is a depiction of a demonstration screen with a name entrywindow displayable on a computing device according to one embodiment.

FIG. 37 is a depiction of a demonstration screen with a chat loadingwindow displayable on a computing device according to one embodiment.

FIG. 38 is a depiction of a demonstration screen with a chat overlaydisplayable on a computing device according to one embodiment.

FIG. 39 is a depiction of a demonstration screen with a chat overlaydisplayable on a computing device according to one embodiment.

FIG. 40 is a depiction of a demonstration screen with an alert windowdisplayable on a computing device according to one embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

The ensuing description provides exemplary embodiments only, and is notintended to limit the scope, applicability, or configuration of thedisclosure. Rather, the ensuing description of the exemplary embodimentswill provide those skilled in the art with an enabling description forimplementing an exemplary embodiment. It should be understood thatvarious changes may be made in the function and arrangement of elementswithout departing from the spirit and scope of the invention as setforth in the appended claims.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood by one of ordinary skill in the art that the embodiments maybe practiced without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the embodimentsin unnecessary detail. In other instances, well-known circuits,processes, algorithms, structures, and techniques may be shown withoutunnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartmay describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations may be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in a figure. A process may correspond to a method, a function,a procedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination can correspond to a return of thefunction to the calling function or the main function.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable medium may include a non-transitory medium in whichdata can be stored and that does not include carrier waves and/ortransitory electronic signals propagating wirelessly or over wiredconnections. Examples of a non-transitory medium may include, but arenot limited to, a magnetic disk or tape, optical storage media such ascompact disk (CD) or digital versatile disk (DVD), flash memory, memoryor memory devices. A computer-program product may include code and/ormachine-executable instructions that may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a class, or any combination of instructions, datastructures, or program statements. A code segment may be coupled toanother code segment or a hardware circuit by passing and/or receivinginformation, data, arguments, parameters, or memory contents.Information, arguments, parameters, data, etc. may be passed, forwarded,or transmitted via any suitable means including memory sharing, messagepassing, token passing, network transmission, etc.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.

Systems depicted in some of the figures may be provided in variousconfigurations. In some embodiments, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.

Certain aspects and features of the present disclosure relate to anapplication that is used to test and experience the use of overlayelements (e.g., application add-ons, such as an interactive chatoverlay) on a graphical interface (e.g., of a website or a computerapplication) before fully integrating the overlay elements into thegraphical interface.

For example, the disclosed concepts can be used in a demonstrationapplication (“demo app”) that is a native application running on a userdevice, such as a mobile device (e.g., a smartphone) or a laptop ordesktop computer. The demonstration application can load a graphicalinterface that is a live version of the graphical interface or an imageof the graphical interface. The live version of the graphical interfacecan be a live website or web application. The demonstration applicationcan determine an overlay element (e.g., a live chat application) topresent with the graphical interface, thus allowing the graphicalinterface to be presented as if the graphical interface had included thecode to enable the overlay element (e.g., the live website can bepresented as if it included code enabling a live chat application). Inan embodiment, the demo app can enable a user to interact with a livewebsite and also interact with an overlay element, such as by startingand engaging in a live chat.

In some embodiments, the user can edit settings of the overlay element,such as by changing how the interface appears on the user device (e.g.,color of chat window) or how the interface operates (e.g., ability toupload a photo during the chat). Settings can be exported, saved, ortransmitted to another device (e.g., a server). Settings can be used ata later time when the overlay element is being incorporated into thegraphical interface.

In some cases, the overlay element may be already incorporated into thegraphical interface (e.g., a live webpage already including a livechat). In such cases, when the graphical interface is loaded into thedemo app, the live settings of the already-incorporated overlay elementcan be accessed and the local settings for the overlay element in thedemo app can be updated with the live settings. Changes can be made tothe local settings of the overlay element displayed on the demo app, andthen can be exported, saved, or transmitted. In an embodiment, localsettings can be used to update the live settings, such as bytransmitting the local settings to a sever and updating the livesettings on the server with the local settings. The demo app can be usedto demonstrate changes in the settings of an overlay element on agraphical interface, and then can be used to update the live settings(e.g., a JSON file on a web server) of a live version of the overlayelement with the local settings of the local version of the overlayelement running in the demo app, thus enabling the demo app to update alive website.

Additionally, interactive features of the overlay element can be tiedinto interactive features of the already-incorporated overlay element.In an example, a company may have an already-incorporated live chatclient included with their live webpage. That live chat client candirect chats to a selected set of chat receivers associated with chatoperators who are knowledgeable about that particular company's services(e.g., a sales person or employee of the company). When the demo app isused, the live chat client of the demo app can use downloaded settingsor a client identifier (e.g., provided by user input into the demo appor downloaded from the live website) to direct chats that are initiatedin the local version of the overlay element running in the demo app tothe same chat receivers associated with the live chat client in the livewebpage.

In some embodiments, the live chat client of the demo app can directchats to generic chat receivers, such as chat receivers associated withchat operators who are knowledgeable about the provider of the overlayelement.

In some embodiments, upon loading the demo app, the demo app presents auser with an option to choose either a live website or a native app.Depending on the option selected, the demo app can determine to use aversion of the overlay element that is written in code executable formwithin a web browser (e.g., if the user selects the live websiteoption), or a version of the overlay element written in native code(e.g., code specifically written for the platform or operating system ofthe user's device).

In an embodiment, upon selecting the live website option, the demo appcan prompt a user to enter a web address (e.g., a Uniform ResourceLocator, or URL) and the demo app then accesses the website through aninternet connection. The demo app also loads a web-enabled version ofthe overlay element (e.g., a version of the overlay element written incode executable from within a web browser). The demo app presents thelive website and the overlay element at the same time. The demo appallows a user to navigate the live website as if they were accessing thelive website through any standard web browser. Additionally, the demoapp allows a user to interact with the overlay element, which can be alive chat room. In some examples, the user can open a chat using theoverlay element and use all of the features of the overlay element, suchas chatting with a chat operator. The chat operator can be an individualprovided by the company supplying the overlay element, can be anindividual provided by the company running the live website, or anotherindividual.

In an embodiment, upon selecting the native app option, the demo app canprovide the user an option to search an application store (“app store”)containing native applications. The demo app can display a list ofnative applications that match the user's search. The user can select anative application from the list. The demo app can then accessscreenshots or videos of the native application that is selected. Insome embodiments, the demo app can access the native application itself.The demo app can present the screenshots, or video of the nativeapplication as a representation of the graphical interface, or the demoapp can present the graphical interface (e.g., the native application)itself. The demo app can also display the overlay element with thegraphical interface or representation of the graphical interface. Theoverlay element can be interactive (e.g., a live chat that can be usedto actually chat with another).

These illustrative examples are given to introduce the reader to thegeneral subject matter discussed here and are not intended to limit thescope of the disclosed concepts. The following sections describe variousadditional features and examples with reference to the drawings in whichlike numerals indicate like elements, and directional descriptions areused to describe the illustrative embodiments but, like the illustrativeembodiments, should not be used to limit the present disclosure. Theelements included in the illustrations herein may be drawn not to scale.

FIG. 1 shows a block diagram of an embodiment of a network interactionsystem 100 which implements and supports certain embodiments andfeatures described herein. Certain embodiments relate to establishing aconnection channel between a network device 105 (which can be operatedby a user 110) and a terminal device 115 (which can be operated by anagent 120). In certain embodiments, the network interaction system 100can include a client device 130 associated with a client 125.

In certain embodiments, a user 110 can be an individual browsing a website or accessing an online service provided by a remote server 140. Aclient 125 can be an entity that provides, operates, or runs the website or the online service, or individuals employed by or assigned bysuch an entity to perform the tasks available to a client 125 asdescribed herein. The agent 120 can be an individual, such as a supportagent or sales associate tasked with providing support or information tothe user 110 regarding the website or online service (e.g., informationabout products available at an online store). Out of a large number ofagents, a subset of agents may be appropriate for providing support orinformation for a particular client 125. The agent 120 may be affiliatedor not affiliated with the client 125. Each agent can be associated withone or more clients 125. In some non-limiting examples, a user 110 canbe an individual shopping an online store from a personal computingdevice, a client 125 can be a company that sells products online, and anagent 120 can be a sales associate employed by the company. In variousembodiments, the user 110, client 125, and agent 120 can be otherindividuals or entities.

While FIG. 1 shows only a single network device 105, terminal device 115and client device 130, an interaction system 100 can include multiple ormany (e.g., tens, hundreds or thousands) of each of one or more of thesetypes of devices. Similarly, while FIG. 1 shows only a single user 110,agent 120 and client 125, an interaction system 100 can include multipleor many of each of one or more of such entities. Thus, it may benecessary to determine which terminal device is to be selected tocommunicate with a given network device. Further complicating matters, aremote server 140 may also be configured to receive and respond toselect network-device communications.

A connection management system 150 can facilitate strategic routing ofcommunications. A communication can include a message with content(e.g., defined based on input from an entity, such as typed or spokeninput). The communication can also include additional data, such as dataabout a transmitting device (e.g., an IP address, account identifier,device type and/or operating system); a destination address; anidentifier of a client; an identifier of a webpage or webpage element(e.g., a webpage or webpage element being visited when the communicationwas generated or otherwise associated with the communication) or onlinehistory data; a time (e.g., time of day and/or date); and/or destinationaddress. Other information can be included in the communication. In someinstances, connection management system 150 routes the entirecommunication to another device. In some instances, connectionmanagement system 150 modifies the communication or generates a newcommunication (e.g., based on the initial communication). The new ormodified communication can include the message (or processed versionthereof), at least some (or all) of the additional data (e.g., about thetransmitting device, webpage or online history and/or time) and/or otherdata identified by connection management system 150 (e.g., account dataassociated with a particular account identifier or device). The new ormodified communication can include other information as well.

Part of strategic-routing facilitation can include establishing,updating and using one or more connection channels between networkdevice 105 and one or more terminal devices 115. For example, uponreceiving a communication from network device 105, connection managementsystem 150 can first estimate to which client (if any) the communicationcorresponds. Upon identifying a client, connection management system 150can identify a terminal device 115 associated with the client forcommunication with network device 105. In some instances, theidentification can include evaluating a profile of each of a pluralityof agents (or experts or delegates), each agent (e.g., agent 120) in theplurality of agents being associated with a terminal device (e.g.,terminal device 115). The evaluation can relate to a content in anetwork-device message. The identification of the terminal device 115can include a technique described, for example, in U.S. application Ser.No. 12/725,799, filed on Mar. 17, 2010, which is hereby incorporated byreference in its entirety for all purposes.

In some instances, connection management system 150 can determinewhether any connection channels are established between network device105 and a terminal device associated with the client (or remote server140) and, if so, whether such channel is to be used to exchange a seriesof communications including the communication. This determination maydepend, at least in part, on a topic associated with the communication,a sentiment score associated with the communication or a past relatedcommunication, a predicted (e.g., relative or absolute) response latencyfor terminal device 115 and/or a type of communication channelassociated with the communication (e.g., instant message, message,email, phone). Selecting an established communication channel maypromote consistency and reduce the need to relay information fromnetwork device 105 multiple times. Meanwhile, determining that a newcommunication channel is to be established can facilitate quickerresponses from more specialized agents.

A decision as to whether to select (or continue to use) an establishedcommunication channel and/or a selection of a new terminal device caninclude determining an extent to which each of one or more terminaldevices (e.g., associated with a client) corresponds to a communicationand/or an associated the user. Such correspondence can relate to, forexample, an extent to which an agent's knowledge base corresponds to acommunication topic, an availability of an agent at a given time and/orover a channel type, a language match between a user and agent, and/or apersonality analysis.

Connection management system 150 may use communication analyses toinfluence routing determinations (e.g., determining whether to route acommunication to a terminal device having previously received acommunication from a network device having transmitted the communicationor selecting a terminal device to receive or transmit a communication).One communication analysis can include determining and assessing one ormore categories or tags of a current or past communication orcommunication series. For example, a communication can be assigned acategory for each of (for example) a demonstration communication usingan interactive demonstration application (discussed in detail withrespect to at least FIGS. 7-40), a topic, channel type (e.g., email, SMSmessage, real-time chat, phone call or asynchronous message), language,complexity level, sentiment, and/or whether/which file type is attached,and a terminal-device selection can be biased towards terminal devicesassociated with similar, same or complementary knowledge bases,channel-type availability, language, skill level, sentiment, and/orfile-type capabilities.

In some examples, communication analysis can include determining whethera communication is received from an interactive demonstrationapplication. In these examples, upon determining that a communication isreceived in association with an interactive demonstration application(e.g., a demonstration application for testing an experience of anoverlay element), communication management system 150 may route thecommunication to a specific or pre-designated agent communicationdevices (e.g., terminal device 115). The communication analysis caninclude determining and applying a rule to the communication receivedfrom an interactive demonstration application in order to influencerouting determinations.

Upon selecting a terminal device 115 to communicate with network device105, connection management system 150 can establish a connection channelbetween the network device 105 and terminal device 115. In someinstances, connection management system 150 can transmit a message tothe selected terminal device 115. The message may request an acceptanceof a proposed assignment to communicate with a network device 105 oridentify that such an assignment has been generated. The message caninclude information about network device 105 (e.g., IP address, devicetype, and/or operating system), information about an associated user 110(e.g., language spoken, duration of having interacted with client, skilllevel, sentiment, and/or topic preferences), a received communication,code (e.g., a clickable hyperlink) for generating and transmitting acommunication to the network device 105, and/or an instruction togenerate and transmit a communication to network device 105.

In one instance, communications between network device 105 and terminaldevice 115 can be routed through connection management system 150. Sucha configuration can allow connection management system 150 to monitorthe communication exchange and to detect issues (e.g., as defined basedon rules) such as non-responsiveness of either device or extendedlatency. Further, such a configuration can facilitate selective orcomplete storage of communications, which may later be used, forexample, to assess a quality of a communication exchange and/or tosupport learning to update or generate routing rules so as to promoteparticular post-communication targets.

In some embodiments, connection management system 150 can monitor thecommunication exchange in real-time and perform automated actions (e.g.,rule-based actions) based on the live communications. For example, whenconnection management system 150 determines that a communication relatesto a particular product, connection management system 150 canautomatically transmit an additional message to terminal device 115containing additional information about the product (e.g., quantity ofproducts in stock, links to support documents related to the product, orother information about the product or similar products).

In one instance, a designated terminal device 115 can communicate withnetwork device 105 without relaying communications through connectionmanagement system 150. One or both devices 105, 115 may (or may not)report particular communication metrics or content to connectionmanagement system 150 to facilitate communication monitoring and/or datastorage.

As mentioned, connection management system 150 may route selectcommunications to a remote server 140. Remote server 140 can beconfigured to provide information in a predetermined manner. Forexample, remote server 140 may access defined one or more text passages,voice recording and/or files to transmit in response to a communication.Remote server 140 may select a particular text passage, recording orfile based on, for example, an analysis of a received communication(e.g., a semantic or mapping analysis).

Routing and/or other determinations or processing performed atconnection management system 150 can be performed based on rules and/ordata at least partly defined by or provided by one or more clientdevices 130. For example, client device 130 may transmit a communicationthat identifies a prioritization of agents, terminal-device types,and/or topic/skill matching. As another example, client device 130 mayidentify one or more weights to apply to various variables potentiallyimpacting routing determinations (e.g., language compatibility,predicted response time, device type and capabilities, and/orterminal-device load balancing). It will be appreciated that whichterminal devices and/or agents are to be associated with a client may bedynamic. Communications from client device 130 and/or terminal devices115 may provide information indicating that a given terminal deviceand/or agent is to be added or removed as one associated with a client.For example, client device 130 can transmit a communication with IPaddress and an indication as to whether a terminal device with theaddress is to be added or removed from a list identifyingclient-associated terminal devices.

In some examples, connection management system 150 can facilitate aninitial match and routing between network device 105 and a firstterminal device 115. For example, a message received in a communicationfrom network device 105 (e.g., a user device which is running aninteractive demonstration application) can be routed to the firstterminal device 115 when the connection management system 150 determinesthat the communication is received via an interactive demonstrationapplication running on network device 105. Determining that thecommunication is received via an interactive demonstration applicationcan include determining whether a particular identifier or codeassociated with the interactive demonstration application is included inthe communication. In some instances, the first terminal device 115 caninclude, for example, a terminal device associated with network device105 (e.g., a communication device used by an agent who is associatedwith an entity of the user), a terminal device associated with adifferent entity (e.g., a communication device used by an agent who isassociated with the connection management system 150), and so on.

Each communication (e.g., between devices, between a device andconnection management system 150, between remote server 140 andconnection management system 150 or between remote server 140 and adevice) can occur over one or more networks 170. Any combination of openor closed networks can be included in the one or more networks 170.Examples of suitable networks include the Internet, a personal areanetwork, a local area network (LAN), a wide area network (WAN), or awireless local area network (WLAN). Other networks may be suitable aswell. The one or more networks 170 can be incorporated entirely withinor can include an intranet, an extranet, or a combination thereof. Insome instances, a network in the one or more networks 170 includes ashort-range communication channel, such as a Bluetooth or a BluetoothLow Energy channel. In one embodiment, communications between two ormore systems and/or devices can be achieved by a secure communicationsprotocol, such as secure sockets layer (SSL) or transport layer security(TLS). In addition, data and/or transactional details may be encryptedbased on any convenient, known, or to be developed manner, such as, butnot limited to, Data Encryption Standard (DES), Triple DES,Rivest-Shamir-Adleman encryption (RSA), Blowfish encryption, AdvancedEncryption Standard (AES), CAST-128, CAST-256, Decorrelated Fast Cipher(DFC), Tiny Encryption Algorithm (TEA), eXtended TEA (XTEA), CorrectedBlock TEA (XXTEA), and/or RCS, etc.

A network device 105, terminal device 115 and/or client device 130 caninclude, for example, a portable electronic device (e.g., a smart phone,tablet, laptop computer, or smart wearable device) or a non-portableelectronic device (e.g., one or more desktop computers, smartappliances, servers, and/or processors). Connection management system150 can be separately housed from network, terminal and client devicesor may be part of one or more such devices (e.g., via installation of anapplication on a device). Remote server 140 may be separately housedfrom each device and connection management system 150 and/or may be partof another device or system. While each device, server and system inFIG. 1 is shown as a single device, it will be appreciated that multipledevices may instead be used. For example, a set of network devices canbe used to transmit various communications from a single user, or remoteserver 140 may include a server stack.

A software agent or application may be installed on and/or executable ona depicted device, system or server. In one instance, the software agentor application is configured such that various depicted elements can actin complementary manners. For example, a software agent on a device canbe configured to collect and transmit data about device usage to aseparate connection management system, and a software application on theseparate connection management system can be configured to receive andprocess the data.

FIG. 2 shows a block diagram of another embodiment of a networkinteraction system 200. Generally, FIG. 2 illustrates a variety ofcomponents configured and arranged to enable a network device 205 tocommunicate with one or more terminal devices 215. The depicted instanceincludes nine terminal devices 215 included in three local-area networks235.

In some instances, a communication from network device 205 includesdestination data (e.g., a destination IP address) that at least partlyor entirely indicates which terminal device is to receive thecommunication. Network interaction system 200 can include one or moreinter-network connection components 240 and/or one or more intra-networkconnection components 255 that can process the destination data andfacilitate appropriate routing.

Each inter-network connection components 245 can be connected to aplurality of networks 235 and can have multiple network cards installed(e.g., each card connected to a different network). For example, aninter-network connection component 245 can be connected to a wide-areanetwork 270 (e.g., the Internet) and one or more local-area networks235. In the depicted instance, in order for a communication to betransmitted from network device 205 to any of the terminal devices, inthe depicted system, the communication must be handled by multipleinter-network connection components 245.

When an inter-network connection component 245 receives a communication(or a set of packets corresponding to the communication), inter-networkconnection component 245 can determine at least part of a route to passthe communication to a network associated with a destination. The routecan be determined using, for example, a routing table (e.g., stored atthe router), which can include one or more routes that are pre-defined,generated based on an incoming message (e.g., from another router orfrom another device) or learned.

Examples of inter-network connection components 245 include a router 260and a gateway 265. An inter-network connection component 245 (e.g.,gateway 265) may be configured to convert between network systems orprotocols. For example, gateway 265 may facilitate communication betweenTransmission Control Protocol/Internet Protocol (TCP/IP) andInternetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX)devices.

Upon receiving a communication at a local-area network 235, furtherrouting may still need to be performed. Such intra-network routing canbe performed via an intra-network connection component 255, such as aswitch 280 or hub 285. Each intra-network connection component 255 canbe connected to (e.g., wirelessly or wired, such as via an Ethernetcable) multiple terminal devices 215. Hub 285 can be configured torepeat all received communications to each device to which it isconnected. Each terminal device can then evaluate each communication todetermine whether the terminal device is the destination device orwhether the communication is to be ignored. Switch 280 can be configuredto selectively direct communications to only the destination terminaldevice.

In some instances, a local-area network 235 can be divided into multiplesegments, each of which can be associated with independent firewalls,security rules and network protocols. An intra-network connectioncomponent 255 can be provided in each of one, more or all segments tofacilitate intra-segment routing. A bridge 280 can be configured toroute communications across segments 275.

To appropriately route communications across or within networks, variouscomponents analyze destination data in the communications. For example,such data can indicate which network a communication is to be routed to,which device within a network a communication is to be routed to orwhich communications a terminal device is to process (versus ignore).However, in some instances, it is not immediately apparent whichterminal device (or even which network) is to participate in acommunication from a network device.

To illustrate, a set of terminal devices may be configured so as toprovide similar types of responsive communications. Thus, it may beexpected that a query in a communication from a network device may beresponded to in similar manners regardless to which network device thecommunication is routed. While this assumption may be true at a highlevel, various details pertaining to terminal devices can give rise toparticular routings being advantageous as compared to others. Forexample, terminal devices in the set may differ from each other withrespect to (for example) which communication channels are supported,geographic and/or network proximity to a network device and/orcharacteristics of associated agents (e.g., knowledge bases, experience,languages spoken, availability, general personality or sentiment, etc.).Accordingly, select routings may facilitate faster responses that moreaccurately and/or completely respond to a network-device communication.A complication is that static routings mapping network devices toterminal devices may fail to account for variations in communicationtopics, channel types, agent availability, and so on.

FIGS. 3A-3C show block diagrams of other embodiments of a networkinteraction system 300 a-c that includes a connection management system.Each of the depicted systems 300 a-c show only 2 local-area networks 235for simplicity, though it can be appreciated that embodiments can beextended to expand the number of local-area networks. Each of systems300 a-c include a connection management system 350, which can identifywhich terminal device is to communicate with network device 205, canestablish and manage (e.g., maintain or close) connection channels, candetermine whether and when to re-route communications in an exchange,and so on. Thus, connection management system 350 can be configured todynamically, and in real-time, evaluate communications, agentavailability, capabilities of terminal devices or agents, and so on, toinfluence routing determinations.

In FIG. 3A, connection management system 350 is associated with each ofnetwork device 205 and a remote server 340 (e.g., connection managementsystem 350 a is associated with network device 205 and connectionmanagement system 350 b is associated with remote server 340). Forexample, connection management system 350 a and/or connection managementsystem 350 b can be installed or stored as an application on each ofnetwork device 205 and remote server 340, respectively. Execution of theapplication(s) can facilitate, for example, a communication betweennetwork device 205 and remote server 340 to identify a terminal device215 selected to participate in a communication exchange with networkdevice 205. The identification can be made based on one or more factorsdisclosed herein (e.g., availability, matching between a communication'stopic/level of detail with agents' or terminal devices' knowledge bases,predicted latency, channel-type availability, and so on).

A client device 330 can provide client data indicating how routingdeterminations are to be made. For example, such data can include:indications as to how particular characteristics are to be weighted ormatched or constraints or biases (e.g., pertaining to load balancing orpredicted response latency). Client data can also include specificationsrelated to when communication channels are to be established (or closed)or when communications are to be re-routed to a different networkdevice. Client data can be used to define various client-specific rules,such as rules for communication routing and so on.

Connection management system 350 b executing on remote server 340 canmonitor various metrics pertaining to terminal devices (e.g., pertainingto a given client), such as which communication channels are supported,geographic and/or network proximity to a network device, communicationlatency and/or stability with the terminal device, a type of theterminal device, a capability of the terminal device, whether theterminal device (or agent) has communicated with a given network device(or user) before and/or characteristics of associated agents (e.g.,knowledge bases, experience, languages spoken, availability, generalpersonality or sentiment, etc.). Accordingly, communication managementsystem 350 b may be enabled to select routings to facilitate fasterresponses that more accurately and/or completely respond to anetwork-device communication based on the metrics.

In the example depicted in FIG. 3A, a communication exchange betweennetwork device 205 and remote server 340 can facilitate earlyidentification of a destination address. Network device 205 may then usethe destination address to direct subsequent communications. Forexample, network device 205 may send an initial communication to remoteserver 340 (e.g., via one or more inter-network connections and awide-area network), and remote server 340 may identify one or morecorresponding clients. Remote server 340 may then identify a set ofterminal devices associated with the one or more corresponding clientsand collect metrics for those terminal devices. The metrics can beevaluated (e.g., by remote server 340) so as to select a terminal deviceto involve in a communication exchange, and information pertaining tothe terminal device (e.g., an IP address) can be sent to network device205. In some embodiments, remote server 340 may continuously orperiodically collect and evaluate metrics for various terminal devicesand store evaluation results in a data store. In such embodiments, uponidentifying a set of terminal devices associated with the one or morecorresponding clients, remote server 340 can access the storedevaluation results from the data store and select a terminal device toinvolve in the communication exchange based on the stored evaluationresults.

In FIG. 3B, connection management system 350 can be configured to serveas a relay and/or destination address. Thus, for example, a set ofnetwork devices 205 may transmit communications, each identifyingconnection management system 350 as a destination. Connection managementsystem 350 can receive each communication and can concurrently monitor aset of terminal devices (e.g., so as to generate metrics for eachterminal device). Based on the monitoring and a rule, connectionmanagement system 350 can identify a terminal device 215 to which it mayrelay each communication. Depending on the embodiment, terminal devicecommunications may similarly be directed to a consistent destination(e.g., of connection management system 350) for further relaying, orterminal devices may begin communicating directly with correspondingnetwork devices. These embodiments can facilitate efficient routing andthorough communication monitoring.

The embodiment depicted in FIG. 3C is similar to that in FIG. 3B.However, in some embodiments, connection management system 350 isdirectly connected to intra-network components (e.g., terminal devices,intra-network connections, or other).

It will be appreciated that many variations of FIGS. 3A-3C arecontemplated. For example, connection management system 350 may beassociated with a connection component (e.g., inter-network connectioncomponent 245 or intra-network connection component 255) such that anapplication corresponding to connection management system 350 (or partthereof) is installed on the component. The application may, forexample, perform independently or by communicating with one or moresimilar or complementary applications (e.g., executing on one or moreother components, network devices or remotes servers).

FIG. 4 shows a representation of a protocol-stack mapping 400 ofconnection components' operation. More specifically, FIG. 4 identifies alayer of operation in an Open Systems Interaction (OSI) model thatcorresponds to various connection components.

The OSI model can include multiple logical layers 402-414. The layersare arranged in an ordered stack, such that layers 402-412 each serve ahigher level and layers 404-414 is each served by a lower layer. The OSImodel includes a physical layer 402. Physical layer 402 can defineparameters physical communication (e.g., electrical, optical, orelectromagnetic). Physical layer 402 also defines connection managementprotocols, such as protocols to establish and close connections.Physical layer 402 can further define a flow-control protocol and atransmission mode.

A link layer 404 can manage node-to-node communications. Link layer 404can detect and correct errors (e.g., transmission errors in the physicallayer 402) and manage access permissions. Link layer 404 can include amedia access control (MAC) layer and logical link control (LLC) layer.

A network layer 406 can coordinate transferring data (e.g., of variablelength) across nodes in a same network (e.g., as datagrams). Networklayer 406 can convert a logical network address to a physical machineaddress.

A transport layer 408 can manage transmission and receipt quality.Transport layer 408 can provide a protocol for transferring data, suchas a Transmission Control Protocol (TCP). Transport layer 408 canperform segmentation/desegmentation of data packets for transmission andcan detect and account for transmission errors occurring in layers402-406. A session layer 410 can initiate, maintain and terminateconnections between local and remote applications. Sessions may be usedas part of remote-procedure interactions. A presentation layer 412 canencrypt, decrypt and format data based on data types known to beaccepted by an application or network layer.

An application layer 414 can interact with software applications thatcontrol or manage communications. Via such applications, applicationlayer 414 can (for example) identify destinations, local resource statesor availability and/or communication content or formatting. Variouslayers 402-414 can perform other functions as available and applicable.

Intra-network connection components 422, 424 are shown to operate inphysical layer 402 and link layer 404. More specifically, a hub canoperate in the physical layer, such that operations can be controlledwith respect to receipts and transmissions of communications. Becausehubs lack the ability to address communications or filter data, theypossess little to no capability to operate in higher levels. Switches,meanwhile, can operate in link layer 404, as they are capable offiltering communication frames based on addresses (e.g., MAC addresses).

Meanwhile, inter-network connection components 426, 428 are shown tooperate on higher levels (e.g., layers 406-414). For example, routerscan filter communication data packets based on addresses (e.g., IPaddresses). Routers can forward packets to particular ports based on theaddress, so as to direct the packets to an appropriate network. Gatewayscan operate at the network layer and above, perform similar filteringand directing and further translation of data (e.g., across protocols orarchitectures).

A connection management system 450 can interact with and/or operate on,in various embodiments, one, more, all or any of the various layers. Forexample, connection management system 450 can interact with a hub so asto dynamically adjust which terminal devices the hub communicates. Asanother example, connection management system 450 can communicate with abridge, switch, router or gateway so as to influence which terminaldevice the component selects as a destination (e.g., MAC, logical orphysical) address. By way of further examples, a connection managementsystem 450 can monitor, control, or direct segmentation of data packetson transport layer 408, session duration on session layer 410, and/orencryption and/or compression on presentation layer 412. In someembodiments, connection management system 450 can interact with variouslayers by exchanging communications with (e.g., sending commands to)equipment operating on a particular layer (e.g., a switch operating onlink layer 404), by routing or modifying existing communications (e.g.,between a network device and a terminal device) in a particular manner,and/or by generating new communications containing particularinformation (e.g., new destination addresses) based on the existingcommunication. Thus, connection management system 450 can influencecommunication routing and channel establishment (or maintenance ortermination) via interaction with a variety of devices and/or viainfluencing operating at a variety of protocol-stack layers.

FIG. 5 represents a multi-device communication exchange system 500according to an embodiment. System 500 includes a network device 505configured to communicate with a variety of types of terminal devicesover a variety of types of communication channels.

In the depicted instance, network device 505 can transmit acommunication over a cellular network (e.g., via a base station 510).The communication can be routed to an operative network 515. Operativenetwork 515 can include a connection management system 520 that receivesthe communication and identifies which terminal device is to respond tothe communication. Such determination can depend on identifying a clientto which that communication pertains (e.g., based on a content analysisor user input indicative of the client) and determining one or moremetrics for each of one or more terminal devices associated with theclient. For example, in FIG. 5, each cluster of terminal devices 530 a-ccan correspond to a different client. The terminal devices may begeographically co-located or disperse. The metrics may be determinedbased on stored or learned data and/or real-time monitoring (e.g., basedon availability).

Connection management system 520 can communicate with various terminaldevices via one or more routers 525 or other inter-network orintra-network connection components. Connection management system 520may collect, analyze and/or store data from or pertaining tocommunications, terminal-device operations, client rules, and/oruser-associated actions (e.g., online activity, account data, purchasehistory, etc.) at one or more data stores. Such data may influencecommunication routing.

Notably, various other devices can further be used to influencecommunication routing and/or processing. For example, in the depictedinstance, connection management system 520 also is connected to a webserver 540. Thus, connection management system 540 can retrieve data ofinterest, such as technical product details, news, current productofferings, current or predicted weather, and so on.

Network device 505 may also be connected to a web server (e.g.,including a streaming web server 545). In some instances, communicationwith such a server provided an initial option to initiate acommunication exchange with connection management system 520. Forexample, network device 505 may detect that, while visiting a particularwebpage, a communication opportunity is available and such an option canbe presented.

One or more elements of communication system 500 can also be connectedto a social-networking server 550. Social networking server 550 canaggregate data received from a variety of user devices. Thus, forexample, connection management system 520 may be able to estimate ageneral (or user-specific) sentiment towards a given topic or estimate ageneral behavior of a given user or class of users.

FIG. 6 shows a block diagram of an embodiment of a connection managementsystem 600. A message receiver interface 605 can receive a message. Insome instances, the message can be received, for example, as part of acommunication transmitted by a source device (e.g., housed separatelyfrom connection management system 600 or within a same housing), such asa network device or terminal device. In some instances, thecommunication can be part of a series of communications or a communicateexchange, which can include a series of messages or message exchangebeing routed between two devices (e.g., a network device and terminaldevice). This message or communication exchange may be part of and/ormay define an interaction between the devices. A communication channelor operative channel can include one or more protocols (e.g., routingprotocols, task-assigning protocols and/or addressing protocols) used tofacilitate routing and a communication exchange between the devices.

In some instances, the message can include a message generated based oninputs received at a local or remote user interface. For example, themessage can include a message that was generated based on button or keypresses or recorded speech signals. In one instance, the messageincludes an automatically generated message, such as one generated upondetecting that a network device is presenting a particular app page orwebpage or has provided a particular input command (e.g., key sequence).The message can include an instruction or request, such as one toinitiate a communication exchange.

In some instances, the message can include or be associated with anidentifier of a client. For example, the message can explicitly identifythe client (or a device associated with the client); the message caninclude or be associated with a webpage or app page associated with theclient; the message can include or be associated with a destinationaddress associated with a client; or the message can include or beassociated with an identification of an item (e.g., product) or serviceassociated with the client (e.g., being offered for sale by the client,having been sold by the client or being one that the client services).To illustrate, a network device may be presenting an app page of aparticular client, which may offer an option to transmit a communicationto an agent. Upon receiving user input corresponding to a message, acommunication may be generated to include the message and an identifierof the particular client. As another example, the message can include orbe associated with an identifier indicating that the message is beingtransmitted in connection with an interactive demonstration applicationrunning on a network device. An interactive demonstration applicationmay facilitate a demonstration of how an overlay element will look andfeel when it is integrated into a website. Upon determining that themessage includes an identifier associated with the interactivedemonstration application, the message can be routed to a particularterminal device or particular set of terminal devices (e.g., terminaldevices used by agents).

A processing engine 610 may process a received communication and/ormessage. Processing can include, for example, extracting one or moreparticular data elements (e.g., a message, a client identifier, anetwork-device identifier, an account identifier, and so on). Processingcan include transforming a formatting or communication type (e.g., to becompatible with a particular device type, operating system,communication-channel type, protocol and/or network).

A message assessment engine 615 may assess the (e.g., extracted orreceived) message. The assessment can include identifying, for example,one or more categories or tags for the message. Examples of category ortag types can include (for example) topic, sentiment, complexity, andurgency. A difference between categorizing and tagging a message can bethat categories can be limited (e.g., according to a predefined set ofcategory options), while tags can be open. A topic can include, forexample, a product, a service, a technical issue, a use question, acomplaint, a refund request or a purchase request. A category or tag canbe determined, for example, based on a semantic analysis of a message(e.g., by identifying keywords, sentence structures, repeated words,punctuation characters and/or non-article words); user input (e.g.,having selected one or more categories); and/or message-associatedstatistics (e.g., typing speed and/or response latency).

In some instances, message assessment engine 615 can determine a metricfor a message. A metric can include, for example, a number ofcharacters, words, capital letters, all-capital words or instances ofparticular characters or punctuation marks (e.g., exclamation points,question marks and/or periods). A metric can include a ratio, such as afraction of sentences that end with an exclamation point (or questionmark), a fraction of words that are all capitalized, and so on.

Message assessment engine 615 can store a message, message metric and/ormessage statistic in a message data store 620. Each message can also bestored in association with other data (e.g., metadata), such as dataidentifying a corresponding source device, destination device, networkdevice, terminal device, client, one or more categories, one or morestages and/or message-associated statistics). Various components ofconnection management system 600 (e.g., message assessment engine 615and/or an interaction management engine 625) can query message datastore 620 to retrieve query-responsive messages, message metrics and/ormessage statistics.

An interaction management engine 625 can determine to which device acommunication is to be routed and how the receiving and transmittingdevices are to communicate. Each of these determinations can depend, forexample, on whether a particular network device (or any network deviceassociated with a particular user) has previously communicated with aterminal device in a set of terminal devices (e.g., any terminal deviceassociated with connection management system 600 or any terminal deviceassociated with one or more particular clients).

In some instances, when a network device (or other network deviceassociated with a sane user or account) has previously communicated witha given terminal device (e.g., about matters relating to a client),communication routing can be generally biased towards the same terminaldevice. Other factors that may influence routing can include, forexample, an inferred or identified user or agent sentiment pertaining tothe previous communication; a topic of a present communication (e.g.,and an extent to which that relates to a topic of a previouscommunication and/or a knowledge base associated with one or moreterminal devices or agents); whether the terminal device (orcorresponding agent) is available; and/or a predicted response latencyof the terminal device. Such factors may be considered absolutely orrelative to similar metrics corresponding to other terminal devices. Are-routing rule (e.g., a client-specific or general rule) can indicatehow such factors are to be assessed and weighted to determine whether toforego agent consistency.

When a network device (or other network device associated with a sameuser or account) has not previously communicated with a given terminaldevice (e.g., about matters relating to a client), a terminal-deviceselection can be performed based on factors such as, for example, anextent to which various agents' knowledge base corresponds to acommunication topic, availability of various agents at a given timeand/or over a channel type, types and/or capabilities of terminaldevices (e.g., associated with the client), a language match between auser and agents, and/or a personality analyses. In one instance, a rulecan identify how to determine a sub-score to one or more factors such asthese and a weight to assign to each score. By combining (e.g., summing)weighted sub-scores, a score for each agent can be determined. Aterminal device selection can then be made by comparing terminaldevices' scores (e.g., to select a high or highest score).

With regard to determining how devices are to communicate, interactionmanagement engine 625 can (for example) determine whether a terminaldevice is to respond to a communication via (for example) email, onlinechat, SMS message, voice call, video chat, etc. A communication type canbe selected based on, for example, a communication-type priority list(e.g., at least partly defined by a client or user); a type of acommunication previously received from the network device (e.g., so asto promote consistency), a complexity of a received message,capabilities of the network device, and/or an availability of one ormore terminal devices. Appreciably, some communication types will resultin real-time communication (e.g., where fast message response isexpected), while others can result in asynchronous communication (e.g.,where delays (e.g., of several minutes or hours) between messages areacceptable).

Further, interaction management engine 625 can determine whether acontinuous channel between two devices should be established, used orterminated. A continuous channel can be structured so as to facilitaterouting of future communications from a network device to a specifiedterminal device. This bias can persist even across message series (e.g.,days, weeks or months). In some instances, a representation of acontinuous channel (e.g., identifying an agent) can be included in apresentation to be presented on a network device. In this manner, a usercan understand that communications are to be consistently routed so asto promote efficiency.

In one instance, a score can be generated using one or more factorsdescribed herein and a rule (e.g., that includes a weight for each ofthe one or more factors) to determine a connection score correspondingto a given network device and terminal device. The score may pertain toan overall match or one specific to a given communication orcommunication series. Thus, for example, the score may reflect a degreeto which a given terminal device is predicted to be suited to respond toa network-device communication. In some instances, a score analysis canbe used to identify each of a terminal device to route a givencommunication to and whether to establish, use or terminate a connectionchannel. When a score analysis is used to both address a routingdecision and a channel decision, a score relevant to each decision maybe determined in a same, similar or different manner.

Thus, for example, it will be appreciated that different factors may beconsidered depending on whether the score is to predict a strength of along-term match versus one to respond to a particular message query. Forexample, in the former instance, considerations of overall schedules andtime zones may be important, while in the latter instance, immediateavailability may be more highly weighted. A score can be determined fora single network-device/terminal-device combination, or multiple scorescan be determined, each characterizing a match between a given networkdevice and a different terminal device.

To illustrate, a set of three terminal devices associated with a clientmay be evaluated for potential communication routing. A score may begenerated for each that pertains to a match for the particularcommunication. Each of the first two terminal devices may havepreviously communicated with a network device having transmitted thecommunication. An input from the network device may have indicatedsatisfaction with an interaction with the communication(s) with thefirst device. Thus, a past-interact sub-score (as calculated accordingto a rule) for the first, second and third devices may be 10, 5, and 0,respectively. (Negative satisfaction inputs may result in negativesub-scores.) It may be determined that only the third terminal device isimmediately available. It may be predicted that the second terminaldevice will be available for responding within 15 minutes, but that thefirst terminal device will not be available for responding until thenext day. Thus, a fast-response sub-score for the first, second andthird devices may be 1, 3 and 10. Finally, it may be estimated a degreeto which an agent (associated with the terminal device) is knowledgeableabout a topic in the communication. It may be determined that an agentassociated with the third terminal device is more knowledgeable thanthose associated with the other two devices, resulting in sub-scores of3, 4 and 9. In this example, the rule does not include weighting ornormalization parameters (though, in other instances, a rule may),resulting in scores of 14, 11 and 19. Thus, the rule may indicate thatthe message is to be routed to a device with the highest score, thatbeing the third terminal device. If routing to a particular terminaldevice is unsuccessful, the message can be routed to a device with thenext-highest score, and so on.

A score may be compared to one or more absolute or relative thresholds.For example, scores for a set of terminal devices can be compared toeach other to identify a high score to select a terminal device to whicha communication can be routed. As another example, a score (e.g., a highscore) can be compared to one or more absolute thresholds to determinewhether to establish a continuous channel with a terminal device. Anoverall threshold for establishing a continuous channel may (but neednot) be higher than a threshold for consistently routing communicationsin a given series of messages. This difference between the overallthreshold and threshold for determining whether to consistently routecommunication may be because a strong match is important in thecontinuous-channel context given the extended utility of the channel. Insome embodiments, an overall threshold for using a continuous channelmay (but need not) be lower than a threshold for establishing acontinuous channel and/or for consistently routing communications in agiven series of messages.

Interaction management engine 625 can interact with an account engine630 in various contexts. For example, account engine 630 may look up anidentifier of a network device or terminal device in an account datastore 635 to identify an account corresponding to the device. Further,account engine 630 can maintain data about previous communicationexchanges (e.g., times, involved other device(s), channel type,resolution stage, topic(s) and/or associated client identifier),connection channels (e.g., indicating—for each of one or moreclients—whether any channels exist, a terminal device associated witheach channel, an establishment time, a usage frequency, a date of lastuse, any channel constraints and/or supported types of communication),user or agent preferences or constraints (e.g., related toterminal-device selection, response latency, terminal-deviceconsistency, agent expertise, and/or communication-type preference orconstraint), and/or user or agent characteristics (e.g., age,language(s) spoken or preferred, geographical location, interests, andso on).

Further, interaction management engine 625 can alert account engine 630of various connection-channel actions, such that account data store 635can be updated to reflect the current channel data. For example, uponestablishing a channel, interaction management engine 625 can notifyaccount engine 630 of the establishment and identify one or more of: anetwork device, a terminal device, an account and a client. Accountengine 635 can (in some instances) subsequently notify a user of thechannel's existence such that the user can be aware of the agentconsistency being availed.

Interaction management engine 625 can further interact with a clientmapping engine 640, which can map a communication to one or more clients(and/or associated brands). In some instances, a communication receivedfrom a network device itself includes an identifier corresponding to aclient (e.g., an identifier of a client, product, service, webpage, orapp page). The identifier can be included as part of a message (e.g.,which client mapping engine 640 may detect) or included as other data ina message-inclusive communication. Client mapping engine 640 may thenlook up the identifier in a client data store 645 to retrieve additionaldata about the client and/or an identifier of the client.

In some instances, a message may not particularly correspond to anyclient. For example, a message may include a general query. Clientmapping engine 640 may, for example, perform a semantic analysis on themessage, identify one or more keywords and identify one or more clientsassociated with the keyword(s). In some instances, a single client isidentified. In some instances, multiple clients are identified. Anidentification of each client may then be presented via a network devicesuch that a user can select a client to communicate with (e.g., via anassociated terminal device).

Client data store 645 can include identifications of one or moreterminal devices (and/or agents) associated with the client. A terminalrouting engine 650 can retrieve or collect data pertaining to each ofone, more or all such terminal devices (and/or agents) so as toinfluence routing determinations. For example, terminal routing engine650 may maintain a terminal data store 655, which can store informationsuch as terminal devices' device types, operating system,communication-type capabilities, installed applications accessories,geographic location and/or identifiers (e.g., IP addresses). Informationcan also include agent information, such as experience level, position,skill level, knowledge bases (e.g., topics that the agent isknowledgeable about and/or a level of knowledge for various topics),personality metrics, working hours, language(s) spoken and/ordemographic information. Some information can be dynamically updated.For example, information indicating whether a terminal device isavailable may be dynamically updated based on (for example) acommunication from a terminal device (e.g., identifying whether thedevice is asleep, being turned off/on, idle/active, or identifyingwhether input has been received within a time period); a communicationrouting (e.g., indicative of whether a terminal device is involved in orbeing assigned to be part of a communication exchange); or acommunication from a network device or terminal device indicating that acommunication exchange has ended or begun.

It will be appreciated that, in various contexts, being engaged in oneor more communication exchanges does not necessarily indicate that aterminal device is not available to engage in another communicationexchange. Various factors, such as communication types (e.g., message,email, chat, phone), client-identified or user-identified targetresponse times, and/or system loads (e.g., generally or with respect toa user) may influence how many exchanges a terminal device may beinvolved in.

When interaction management engine 625 has identified a terminal deviceto involve in a communication exchange or connection channel, it cannotify terminal routing engine 650, which may retrieve any pertinentdata about the terminal device from terminal data store 655, such as adestination (e.g., IP) address, device type, protocol, etc. Processingengine 610 can then (in some instances) modify the message-inclusivecommunication or generate a new communication (including the message) soas to have a particular format, comply with a particular protocol, andso on. In some instances, a new or modified message may includeadditional data, such as account data corresponding to a network device,a message chronicle, and/or client data.

A message transmitter interface 660 can then transmit the communicationto the terminal device. The transmission may include, for example, awired or wireless transmission to a device housed in a separate housing.The terminal device can include a terminal device in a same or differentnetwork (e.g., local-area network) as connection management system 600.Accordingly, transmitting the communication to the terminal device caninclude transmitting the communication to an inter- or intra-networkconnection component.

FIG. 7 is a block diagram of a demonstration application environment 700according to one embodiment. The demonstration application environment700 can include a user device 706, such as a computer or mobile device,running a demonstration application 728. The demonstration application728 can present a graphical interface 726 and an overlay element 724.The overlay element 724 can be interactive and running live on the userdevice 706. The overlay element 724 includes code, applicationlibraries, or other aspects that are running on the user device 706. Theoverlay element 724 can be present as an actual overlay in front of thegraphical interface 726, or can be presented near or around thegraphical interface 726. In some embodiments, the overlay element 724 isonly visible after a specific user input, such as a specific keycombination, a specific swiping movement, a multitouch input, or otherspecific user input.

In an embodiment, the graphical interface 726 is a webpage 712. Thedemonstration application 728 can cause the user device 706 to promptthe user for a web address of a web server 702. The user device 706 canestablish a data connection 716 with the web server 702 to obtain andload the webpage 712. The user device 706 would therefore be loading thewebpage 712 and the overlay element 724 simultaneously. The webpage 712can be presented live (e.g., running on the user device 706) and can befully interactive, as well as the overlay element 724, as if the webpage712 had already included the overlay element 724 and was simply runningin a web browser on the user device 706.

In an embodiment, the graphical interface 726 is a graphicalrepresentation 714 of a native application. The demonstrationapplication 728 can cause the user device 706 to prompt the user for anative application, such as by name, by selecting from a list, or byquerying. The user device 706 can establish a data connection 718 with amobile application store 704 in order to perform queries for a nativeapplication. The data connection 718 can be used to access the graphicalrepresentation 714 of the native application. The graphicalrepresentation 714 can be an image (e.g. a screenshot) or a videodepicting the graphical interface of the native application. The userdevice 706 can load the graphical representation 714 and the overlayelement 724 simultaneously. The overlay element 724 can be presented toappear as if it were already included in the graphical interfacedepicted by the graphical representation 714, and the overlay element724 can be presented live and can be fully interactive. The graphicalrepresentation 714, being a representation of the graphical interfaceand not the graphical interface itself, can be presented as a stillimage or a video, but may not be fully interactive.

In some embodiments, the graphical interface 726 is another nativeapplication 730 residing within memory of the user device 706. The userdevice 706 can prompt a user to select the native application 730 from alist of native applications located in a memory of the user device 706.The demonstration application 728 can present the native application 730and overlay element 724 simultaneously, as if the overlay element 724were already integrated into the native application 730. Both the nativeapplication 730 and the overlay element 724 may be presented live andmay be fully interactive.

In an embodiment, the overlay element 724 can be a live chat client. Theoverlay element 724 can include interface elements, such as text boxesand chat bubbles, that allow a user to interact with a live humanoperating a chat receiver 710. Upon initiating a proper command (e.g.,clicking or tapping on the overlay element 724), the user device 706 canestablish a chat connection 722 with a chat receiver 710. In someembodiments, by default, the demonstration application 728 can establisha chat connection 722 with a chat receiver 710 associated with thedemonstration application 728. In some embodiments, the demonstrationapplication 728 can establish a chat connection 722 with a chat receiver710 associated with another company, as defined by settings of theoverlay element 724.

In some embodiments, the user device 106 can establish a data connection720 with an app server 708. The app server 708 can be a server thatsupports the operation of the overlay element 724, such as by providinginformation on which chat receiver 710 to contact. In some embodiments,the user device 706 can provide client identification information (e.g.,a number or a name) to the app server 708, which can then be used toprovide settings information to the user device 706, which can determinehow the demonstration application 728 operates. For example, a clientidentification number stored on the user device 706 can be transmittedto the app server 708 and the app server 708 can return an address ofthe chat receiver 710 to use. The demonstration application 728 can thencause the overlay element 724 to initiate a chat connection 722 with thechat receiver 710 based on the address provided by the app server 708.This address can be different than the default address built into thedemonstration application 728. In this way, a client using thedemonstration application 728 to test a live chat overlay on theirwebpage 712 would be able to connect to the chat receiver 710 associatedwith their company, rather than a generic chat receiver 710. In someembodiments, the client identification information can be stored in theuser device 706 (e.g., input into the demonstration application 728 by auser) or can be stored in association with the webpage 712, web server702, or native application 730.

In some embodiments, the user device 706 can obtain settings informationfrom the web server 702 via the data connection 716. Settingsinformation can be stored on the web server 702 or on a separate serverassociated with the web server 702. In some embodiments, the settingsinformation can be stored on the app server 708. In some embodiments,the settings information can be stored as a JavaScript Object Notation(JSON) file. The settings information can be stored as another type ofdata file, such as an XML or YAML file.

In some embodiments, a webpage 712 or native application 730 can have alive overlay element already incorporated into the graphical interface.The webpage 712 or native application can have live settings information732 (e.g., settings information used by the live overlay element tocontrol the live overlay element's functionality or appearance). In someembodiments, the user device 706 can access the live settingsinformation 732. The user device 706 can use the live settingsinformation 732 to update local settings 734. The local settings 734 cancontrol the functionality or appearance of the overlay element 724 thatis running in the demonstration application 728.

In some embodiments, the user device 706 can use the local settings 734to update live settings 732, as described in further detail below.

FIG. 8 is a flow chart of a process 800 for demonstrating an applicationon a computing device. The computing device can be running ademonstration application. At block 802, the computing device can accessa graphical interface. Accessing a graphical interface at block 802 canoptionally include accessing a website at block 814, which can includerunning the website on the computing device. Accessing a graphicalinterface at block 802 can optionally include querying a mobileapplication store 816, which can include obtaining a graphicalinterpretation of a graphical interface in the form of an image or avideo. In some embodiments, the graphical interface accessed at block802 is a native application.

In some embodiments, the computing device can optionally prompt the userfor an implementation type at block 818. Prompting the user for animplementation type at block 818 can include having the user selectbetween a live website implementation type and a native appimplementation type. The implementation type selected at block 818 canbe used to determine how the graphical interface is accessed at block802. In some embodiments, the implementation type selected at block 818can determine which version of an overlay element to present at block804.

At block 804, an overlay element is determined. Determining an overlayelement can include accessing code for the overlay element. In someembodiments, determining an overlay element can include selecting aversion of the overlay element from multiple versions of the overlayelement. In some embodiments, a web version of the overlay element(e.g., a version of the overlay element designed to be integrated intothe code of a webpage) can be presented if the graphical interfaceaccessed at block 802 is a website. In some embodiments, a nativeversion of the overlay element (e.g., a version of the overlay elementdesigned to be integrated into the code of a native application) can bepresented if the graphical interface accessed at block 802 is a nativeapplication or a graphical representation of a native application.

At block 806, the overlay element is presented with the graphicalinterface. The overlay element can be presented in front of thegraphical interface. The overlay element can be presented adjacent tothe graphical interface. In some embodiments, presenting the overlayelement with the graphical interface at block 806 optionally includespresenting a live chat window at block 808.

At block 810, the computing device presents configurable settings.Configurable settings can include settings that control thefunctionality of the overlay element. Configurable settings can includesettings that control the appearance of the overlay element. In someembodiments, the configurable settings that are presented at block 810are determined based on whether the graphical interface accessed atblock 802 is a website, a native application, or a graphicalrepresentation of a native application. In some embodiments, theconfigurable settings that are presented at block 810 are determinedbased on client identification information. For example, based on clientidentification information, the demonstration application running on thecomputing device can present a first set of configurable settings to afirst client and present a second set of configurable settings to asecond client. The demonstration application can transmit the clientidentification information to a server external to the computing deviceand can receive a signal indicating what configurable settings topresent at block 810. Thus, a client with a first level of service(e.g., live chatrooms without images) can be given a first set ofconfigurable settings (e.g., standard live chat settings), while aclient with a second level of service (e.g., live chatrooms with images)can be given a second set of configurable settings (e.g., standard livethat settings and settings specific to image sharing).

Examples of suitable configurable settings for an overlay element thatis a live chat element can include: an option to select the type of webbrowser to simulate when the graphical interface is a live website, anoption to enable conversion tracking, an option to enable surveys, anoption to enable photo sharing, an option to enable call deflectionreporting, options to adjust the appearance of buttons, options toadjust the appearance of the chat keyboard, options to change a logothat is presented, options to adjust fonts present in the live chat,options to adjust colors present in the live chat, options to adjustoverlay appearance (e.g., blur, color, and alpha), and other options.

At block 812, the overlay element can be updated based on theconfigurable settings. For example, code for the overly element may beupdated with the configurable settings (e.g., to match the configurablesettings).

FIG. 9 is a process 900 for updating a live overlay element from ademonstration application according to one embodiment. The demonstrationapplication can be running on a computing device. At block 902, agraphical interface can be accessed. The graphical interface accessed atblock 902 can be a live webpage. The live webpage can include a liveoverlay element that has already been incorporated into the livewebpage. At block 904, an overlay element can be determined as describedabove.

At optional block 906, live settings corresponding to the live webpagecan be accessed. Live settings can be accessed directly from thewebpage, from a web server associated with the webpage, or from anotherserver associated with the webpage.

At optional block 908, the local configurable settings can be updated.The local configurable settings can be updated based on the livesettings accessed at block 906. Thus, the local configurable settingscan be updated to be identical to the live settings corresponding to thelive webpage so that the overlay element presented at block 910, below,will be visually similar, functionally similar, or both to the liveoverlay element.

At block 910, the overlay element can be presented with the graphicalinterface. If the local configurable settings were updated at block 908with the live settings, the overlay element will be presented in avisually similar, functionally similar, or visually and functionallysimilar manner to the live overlay element. In some embodiments, thedemonstration application is able to suppress the live overlay elementfrom appearing in the graphical interface presented at block 910.

At block 912, configurable settings are presented and can be changed, asdescribed above with reference to FIG. 8. At block 814, the overlayelement can be updated based on the configurable settings, as describedabove with reference to FIG. 8.

At block 816, the live settings can be updated based on the configurablesettings (e.g., local settings used to configure the local overlayelement presented at block 810). The live settings can be updated by thecomputing device transmitting update commands or an updated settingsfile to a web server or other server.

In some embodiments, configurable settings can be exported at block 818.The settings can be exported as a JSON file, other markup language file,or as a human-readable list of the settings. The exported settings canbe saved for future use. The exported settings can be provided to adeveloper as instructions to update a live webpage.

In an embodiment, the process 900 allows a client to access their ownlive webpage from a demonstration application, see a local overlayelement running in the demonstration application, edit the configurablesettings of the local overlay element, and upload the configurablesettings to be used as live settings with their own live webpage. Thus,the client is able to quickly and easily update the functionality,appearance, or functionality and appearance of an overlay elementrunning on their live webpage based on a demonstration of how theoverlay element would function, appear, or function and appear given theupdated settings.

FIG. 10 is a block diagram of a process 1000 of demonstrating a chatinterface as an overlay element according to one embodiment. Ademonstration application can be running on a computing device. Whilethe example embodied in FIG. 10 deals with live chat overlay elements,it can be applied to other overlay elements.

At block 1002, the demonstration application can prompt the user toselect a web chat mode of implementation or a native chat mode ofimplementation.

If the user selects the web chat mode of implementation, a website canbe accessed at block 1004. At block 1010, the demonstration applicationcan determine to use a web version of the chat interface, based on theuser's selection of a web chat mode of implementation. In someembodiments, the web version of the chat interface can be suitable forinsertion in a website. At optional block 1014, the demonstrationapplication can prompt the user to edit settings corresponding to thechat interface. At block 1018, the chat interface can be presented withthe website. The chat interface can be presented as an overlay elementas described herein. The chat interface and the website can both befully operational.

If the user selects the native chat mode of implementation, anapplication store can be accessed at block 1006. Accessing theapplication store can include prompting the user for input (e.g., asearch query) and submitting that input to the application store toidentify a native application. Accessing the application store caninclude accessing information about a native application. At block 1008,the demonstration application can load a graphical representation basedon the native application identified at block 1006. The graphicalrepresentation can be a video or image corresponding to the nativeapplication, such as a screenshot of the graphical interface of thenative application. At block 1012, the demonstration application candetermine to use a native version of the chat interface, based on theuser's selection of a native chat mode of implementation. The nativeversion of the chat interface can be programmed in code suitable forinsertion in the code of a native application. In some embodiments, thenative version can be based on an application library suitable forincorporation into a native application. At optional block 1016, thedemonstration application can prompt the user to edit settingscorresponding to the chat interface. At block 1020, the chat interfacecan be presented with the graphical representation. The chat interfacecan be presented as an overlay element as described herein. The chatinterface can be fully operational and interactive, while the graphicalrepresentation can be a non-interactive image or video.

FIG. 11 illustrates an example of a user device 1100 (e.g., computingdevice) according to one embodiment. The user device 1100 may includeany human-to-machine interface with network connection. The user device1100 can have capability that allows accessing of a webpage. Forexample, the user device 1100 may include a cellular telephone, asmartphone, a desktop computer, a laptop computer, a tablet, a personaldigital assistant (PDA), or any other suitable device. The user device1100 can include hardware elements that can be electrically coupled viaa bus 1118 (or may otherwise be in communication, as appropriate). Inone embodiment, the bus 1118 can be used for the processor(s) 1102 tocommunicate between cores and/or with the memory 1112. The hardwareelements may include one or more processors 1102, including withoutlimitation one or more general-purpose processors and/or one or morespecial-purpose processors (such as digital signal processing chips,graphics acceleration processors, and/or the like); one or more inputdevices 1116, which can include without limitation a camera, a mouse, akeyboard, a touch sensitive screen, a touch pad, a keypad, and/or thelike; and one or more output devices 1114, which can include, withoutlimitation, a display, a printer, and/or the like.

The user device 1100 may include one or more network transceivers 1106connected to the bus 1118. The network transceiver 1106 may be operableto send and/or receive signals across a network connection, such as toand/or from a cloud or the Internet.

The user device 1100 may further include (and/or be in communicationwith) one or more non-transitory machine-readable storage mediums orstorage devices (e.g., memory 1112), which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, a solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. Such storage devices may be configuredto implement any appropriate data storage, including without limitation,various file systems, database structures, and/or the like.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in memory 1112,such as RAM, ROM, FLASH, or disc drive, and executed by processor(s)1102. The user device 1100 can also comprise software elements (e.g.,located within the memory 1112), including, for example, an operatingsystem, device drivers, executable libraries, and/or other code, such asone or more application programs, which may comprise computer programsimplementing various functions. Such functions or code may include codeto perform the steps described above with respect to FIGS. 7-10 andFIGS. 13-14. Memory 1112 may be a non-transitory machine-readablestorage medium, processor-readable memory, and/or a computer-readablememory that stores the one or more computer-program products configuredto cause the processor(s) 1102 to perform the various functions. Inother embodiments, the various functions described may be performed inhardware.

FIG. 12 illustrates an example of a server 1200, such as a web server oran app server, according to one embodiment. An application store canalso be a server 1200. The server 1200 can include hardware elementsthat can be electrically coupled via a bus 1216 (or may otherwise be incommunication, as appropriate). In one embodiment, the bus 1216 can beused for the processor(s) 1202 to communicate between cores and/or withthe memory 1212. The hardware elements may include one or moreprocessors 1202, including without limitation one or moregeneral-purpose processors and/or one or more special-purpose processors(such as digital signal processing chips, graphics accelerationprocessors, and/or the like), memory 1212, a bus 1216, and a networktransceiver 1214. The network interface 1214 can enable communicationwith a network (e.g., a cloud or the Internet).

The server 1200 may further include (and/or be in communication with)one or more non-transitory machine-readable storage mediums or storagedevices (e.g., memory 1212), which can comprise, without limitation,local and/or network accessible storage, and/or can include, withoutlimitation, a disk drive, a drive array, an optical storage device, asolid-state storage device such as a random access memory (“RAM”) and/ora read-only memory (“ROM”), which can be programmable, flash-updateableand/or the like. Such storage devices may be configured to implement anyappropriate data storage, including without limitation, various filesystems, database structures, and/or the like.

In various embodiments, functions may be stored as one or more one ormore computer-program products, such as instructions or code, in memory1212. The server 1200 can also comprise software elements (e.g., locatedwithin the memory), including, for example, an operating system, devicedrivers, executable libraries, and/or other code, such as one or moreapplication programs, which may comprise computer programs implementingthe functions provided by various embodiments, and/or may be designed toimplement methods and/or configure systems, as described herein. Merelyby way of example, one or more procedures described with respect to theprocesses discussed above may be implemented as code and/or instructionsexecutable by a computer (and/or a processor within a computer); in anaspect, then, such code and/or instructions can be used to configureand/or adapt a computing device (or other device) to perform one or moreoperations in accordance with the described methods. Such functions orcode may include code to perform the steps described above with respectto FIGS. 7-10 and FIGS. 13-14. The memory 1212 may be a non-transitorymachine-readable storage medium, processor-readable memory, and/or acomputer-readable memory that stores the one or more computer-programproducts configured to cause the processor(s) 1202 to perform thefunctions described. In other embodiments, one or more of the functionsdescribed may be performed in hardware.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the memory 1212.In some cases, the storage medium might be incorporated within acomputer system. In other embodiments, the storage medium might beseparate from a computer system (e.g., a removable medium, such as acompact disc), and/or provided in an installation package, such that thestorage medium can be used to program, configure and/or adapt acomputing device with the instructions/code stored thereon. Theseinstructions of one or more computer-program products might take theform of executable code, which is executable by the server 1200 and/ormight take the form of source and/or installable code, which, uponcompilation and/or installation on the server 1200 (e.g., using any of avariety of generally available compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

FIG. 13 is a block diagram of an overlay element demonstration process1300 according to one embodiment. A computing device 1322 is shownaccessing a web server 1318 through a first data connection 1320. Thecomputing device 1322 is able to load a live website 1324 that includesa live overlay element 1326.

A user device 1302 can access the same web server 1318 through a seconddata connection 1316. The user device 1302 can be running ademonstration application 1328 that is able to load the live webpage1324. In some embodiments, the demonstration application 1328 can loadthe live webpage 1324 while suppressing the live overlay element 1326.The demonstration application 1328 can present a local overlay element1304. The functionality, appearance, or functionality and appearance ofthe local overlay element 1304 can be based on configurable settings.The demonstration application 1328 can cause the user device 1302 toobtain live settings 1306 from the web server 1318 through the seconddata connection 1316 and update the local settings of the local overlayelement 1304 with the live settings 1306.

The user device 1302 can display a local settings pane 1314. The localsettings pane 1314 can allow the user to adjust the local settings.Examples of local settings include a color setting 1308, a size setting1310, and a secondary feature setting 1312. Other settings can be usedand set. The color setting 1308, size setting 1310, and secondaryfeature setting 1312 can be updated based on the live settings 1306 fromthe web server 1318. In FIG. 13, the color setting 1308 can be a firstcolor, the size setting 1310 can be a medium size, and the secondaryfeature setting 1312 can be off. The color setting 1308 and size setting1310 can represent settings that change the appearance of the overlayelement 1304. The secondary feature setting 1312 can represent settingsthat change the functionality of the overlay element 1304.

FIG. 14 is a block diagram of an overlay element updating process 1400based on the overlay element demonstration process 1300 of FIG. 13according to one embodiment. The settings on the local settings pane1314 can be updated by a user. For example, the color setting 1308 canbe changed to a second color, the size setting 1310 can be changed tolarge, and the secondary feature setting 1312 can be changed to on.

Based on the updated local settings, the overlay element 1304 presentedin the demonstration application 1328 running on the user device 1302can look and operate differently. The demonstration application canstill be displaying the website 1324 and the overlay element 1304. Thechange in color setting 1308 can correspond to a change in the color ofthe overlay element 1304. The change in size setting 1310 can correspondto a change in the length of the overlay element 1304. The change in thesecondary feature setting 1312 can correspond to the presence of asecondary button 1330 on the overlay element 1304. Other settings andother changes can be used.

The user device 1302 can upload the local settings, through the seconddata connection 1316, to the web server 1318 to update the live settings1306. The live settings 1306 can now contain the settings that have beenchanged by the user.

Now, when a computer 1322 accesses the web server 1318 through the firstdata connection 1320, the computer will load the webpage 1324 and thelive overlay element 1326. However, since the functionality andappearance of the live overlay element 1326 is based on the livesettings 1306, the live overlay element 1326 will have the change colorset by the color setting 1308, the changed size set by the size setting1310, and the secondary button 1330 set by the secondary functionsetting 1312. Thus, the user device 1302 is able to demonstrate settingschanges in a local overlay element 1304, and then update live settings1306 so that other users can experience those same changes in the liveoverlay element 1326.

FIGS. 15-40 are depictions of screenshots that may appear on a computingdevice, such as on a smartphone.

FIG. 15 is a depiction of a selection screen 1500 displayable on acomputing device according to one embodiment. On the selection screen1500, the computing device provides options for selecting the mode ofimplementation. The selection screen 1500 can include a web chat button1502 and a native chat button 1504. Upon selecting the web chat button1502, the computing device can load a URL entry screen 1600. Uponselecting the native chat button 1504, the computing device can load anative app search screen 2600.

FIG. 16 is a depiction of a URL entry screen 1600 displayable on acomputing device according to one embodiment. The URL entry screen 1600can prompt a user to enter a URL of a web site to load along with anoverlay element. The URL entry screen 1600 can include a URL field 1604in which a URL entered. A keyboard 1606 can be presented for enteringcharacters into the URL field 1604. After a URL is entered into the URLfield 1604, a user can select the next button 1602 to cause thecomputing device to load a web chat initial settings screen 1700.

FIG. 17 is a depiction of a web chat initial settings screen 1700displayable on a computing device according to one embodiment. The webchat initial settings screen 1700 allows the entry of various settingsthat will be used to initially load the demonstration screen 1800. Theweb chat initial settings screen 1700 can include a browser selector1704, a conversion tracking switch 1706, a surveys switch 1708, and ashow tab selector 1710. The browser selector 1704 can allow a user toselect which browser will be used to load the webpage in thedemonstration screen 1800. The conversion tracking switch 1706 can allowa user to enable or disable conversion tracking on the overlay element.The surveys switch 1708 can allow a user to enable or disable a promptfor survey entries before or after entering a live chat. The show tabselector 1710 can allow a user to select the level of depth in a websitebefore the live chat tab will be shown. For example, setting the showtab selector 1710 to “all” will display the live chat tab on all pagesof the website. However, setting the show tab selector 1710 to “deep” or“deeper” will only show the live chat tab on successively deeper linksinto the webpage (e.g., after clicking one, two, or more links within awebsite). Upon selecting the done button 1702, the computing device canload a demonstration screen 1800.

FIG. 18 is a depiction of a demonstration screen 1800 displayable on acomputing device according to one embodiment. The demonstration screencan 1800 can include a live webpage 1804 presented along with a livechat tab 1802. The live chat tab 1802 can be presented as an overlayelement. The live webpage 1804 can be live and fully interactive. A usercan navigate the webpage 1804 and operate any interactive elements ofthe webpage 1804, such as buttons and links. Likewise, the live chat tab1802 is live and interactive. When a user selects the live chat tab1802, the computing device can load a pre-chat survey window 1902.

FIG. 19 is a depiction of a demonstration screen 1900 with a pre-chatsurvey window 1902 displayable on a computing device according to oneembodiment. The pre-chat survey window 1902 may be presented over thelive webpage 1904. The live webpage 1904 can be partially obscured, suchas through blurring, fading, or overlaying a translucent color. Thepre-chat survey window 1902 can include a cancel button 1906, which whenpressed causes the computing device to dismiss the pre-chat surveywindow 1902. The pre-chat survey window 1902 can further include a nextbutton 1908, which when pressed causes the computing device to load aname entry window 2010.

FIG. 20 is a depiction of a demonstration screen 2000 with a name entrywindow 2010 displayable on a computing device according to oneembodiment. The name entry window 2010 may be presented over the livewebpage. The name entry window 2010 can include a name entry box 2002into which a user can type his or her name for identification purposesduring the live chat. A keyboard 2008 can be displayed for the purposesof entering characters into the name entry box 2002. The name entrywindow 2010 can include a back button 2006, which when pressed can causethe computing device to dismiss the name entry window 2010. The nameentry window 2010 can further include a done button 2004, which whenpressed can cause the computing device to load a chat overlay 2114.

FIG. 21 is a depiction of a demonstration screen 2100 with a chatoverlay 2114 displayable on a computing device according to oneembodiment. Upon loading the chat overlay 2114, the computing device caneither establish a new chat connection or continue an already existingchat connection. The chat overlay 2114 can enable a user to interactwith an agent through a live chat. The chat overlay 2114 can bepresented over the live webpage 2106. The live webpage 2106 can beobscured as described above. The chat overlay 2114 can include an endsession button 2104, which when pressed can cause the computing deviceto dismiss the chat overlay 2114 and terminate the chat connection. Thechat overlay 2114 can include a message bubble 2102 includinginformation pertaining to the live chat. Similar message bubbles can beused to display sent and received messages. The chat overlay 2114 caninclude a hide chat button 2108, which when pressed causes the computingdevice to dismiss the chat overlay 2114 without terminating the chatconnection, allowing a user to resume the chat connection at a latertime. The chat overlay 2114 can further include a message box 2110 intowhich messages may be typed, as well as a send button 2112, which whenpressed can cause the computing device to transmit any message typedinto the message box 2110.

FIG. 22 is a depiction of a demonstration screen 2200 with a functionbar 2208 displayable on a computing device according to one embodiment.Demonstration screen 2200 can display a function bar 2208 upon receivinga specified input from a user, such as after a user swipes across thedemonstration screen 2200. Other specified inputs can be used, such asinput from an accelerometer when the user shakes the computing device.Upon receiving the specified input, the function bar 2208 can appear.The function bar 2208 can contain buttons for using or configuring thedemonstration application itself. The function bar 2208 can include achat button 2212, which when pressed can cause the computing device toopen the chat overlay 2114 without the need for the user to press thelive chat tab 2202, thus bypassing the live chat tab 2202. The functionbar 2208 can include a purchase button 2214, which when pressed cancause the computing device to simulate a purchase made on the livewebsite 2204, for the purpose of demonstrating functionality of theoverlay element (e.g., when the overlay element is capable of detectingpurchases). The function bar 2208 can include a call button 2216, whichcan be used to simulate a phone call being made from the live website2204, or can be used to initiate a live phone call, such as to arepresentative of the company supplying the demonstration application.The function bar 2208 can include a settings button 2210, which whenpressed can cause the computing device to load a settings screen 2300.

FIG. 23 is a depiction of a settings screen 2300 displayable on acomputing device according to one embodiment. The settings screen 2300can contain various settings 2304, which can correspond to settings ofhow the demonstration application operates, how the overlay elementoperates, and how the overlay element appears. The settings screen 2300can include a type setting 2306, allowing a user to switch between a webchat mode of implementation and a native chat mode of implementation.Changing the mode of implementation can also effect what settings aredisplayed on the settings screen 2300. The settings screen 2300 caninclude a URL entry box 2308, allowing a user to change the websitewhich will be accessed and displayed in a demonstration screen. Thesettings screen 2300 can also include a browser selector 2310, allowinga user to change which browser is used to display the live webpage inthe demonstration screen. The settings screen 2300 can include othersettings. The settings screen 2300 can include a demo button 2302, whichwhen pressed can cause the computing device to load a demonstrationscreen using the current settings.

FIG. 24 is a depiction of a selection screen 2400 showing new URL andbrowser selections displayable on a computing device according to oneembodiment. Selection screen 2400 is the selection screen 2300 of FIG.23, showing a new URL entered into the URL entry box 2404 and a newbrowser selected in the browser selector 2406. When the demo button 2402is pressed, the computing device will load demonstration screen 2500.

FIG. 25 is a depiction of a selection screen 2500 displayable on acomputing device according to one embodiment. Demonstration screen 2500includes a live webpage 2504 corresponding to the URL entered into theURL entry box 2404. The live webpage 2504 is being displayed within thebrowser 2502 selected in the browser selector 2406. Demonstration screen2500 displays the live webpage 2504 along with the live chat tab 2506.

FIG. 26 is a depiction of a native app search screen 2600 displayable ona computing device according to one embodiment. When a user selects thenative chat button 1504, the computing device can load the native appsearch screen 2600. The native app search screen 2600 can include aquery box 2604 into which a user can enter a search query, such as thename of a native application. A keyboard 2610 can be used to entercharacters into the query box 2604. The native app search screen 2600can include a store selector 2606, which when pressed can cause thecomputing device to load a store selection screen 2700. The storeselector 2606 can default to the a default store available on thecomputing device, such as an app store specific for the region in whichthe computing device is used. The native app search screen 2600 caninclude a previous app button 2608, which when pressed can cause thecomputing device to load an app settings screen 2900 using the app thatwas previously used. The native app search screen 2600 can include anext button 2602, which when pressed can cause the computing device toload an app selection screen 2800 based on the search query typed intothe query box 2604 and the store selected in the store selector 2606.

FIG. 27 is a depiction of a store selection screen 2700 displayable on acomputing device according to one embodiment. The store selection screen2700 can include numerous native app stores 2702 available to besearched. For example, there may exist separate native app stores 2702for various countries or regions, which can be selected. In otherexamples, there may exist separate native app stores 2702 provided byvarious providers, which can be selected. When one of the native appstores 2702 is selected, the computing device can load the native appsearch screen 2600 and show the selected store in the store selector2606.

FIG. 28 is a depiction of an app selection screen 2800 displayable on acomputing device according to one embodiment. The app selection screen2800 can display a list of native apps 2802 that both match the searchquery from the query box 2604 and are available in the app storeselected in the store selector 2606. The closest matching native app2804 can be at the top of the list of native apps 2802. When a userselects an app, such as the closest matching native app 2804, thecomputing device can load an app settings screen 2900 based on theselected app. Additionally, when the user selects an app, the computingdevice can access and download the graphical representationscorresponding to the selected app that are available in the app store.

FIG. 29 is a depiction of an app settings screen 2900 displayable on acomputing device according to one embodiment. The app settings screen2900 can include a graphical representation selector 2904, which canallow a user to select which graphical representations (e.g., images orvideos) are to be used in the demonstration screen 3300. As seen in FIG.29, the graphical representation selector 2904 presently shows threeselected graphical representations 2906 and two non-selected graphicalrepresentations 2908. The graphical representations available to beselected can be obtained from the app store as described above. In someembodiments, the graphical representations can be obtained from photosor screenshots stored on the computing device (e.g., if a user hadpreviously opened an app and taken a screenshot of the app). The appsettings screen 2900 can include various settings 2910, which cancontrol the appearance or functionality of the demonstration app or theoverlay element. The app settings screen 2900 can include a done button2902, which when pressed can cause the computing device to loaddemonstration screen 3300.

FIG. 30 is a depiction of an initial settings screen 3000 displayable ona computing device according to one embodiment. Initial settings screen3000 is an extension of initial settings screen 2900, available byscrolling downwards. Additional settings 3004 can be presented, whichcan control the appearance or functionality of the demonstration app orthe overlay element.

FIG. 31 is a depiction of an initial settings screen 3100 displayable ona computing device according to one embodiment. Initial settings screen3100 is an extension of initial settings screen 3000, available byscrolling downwards. Additional settings 3104 can be presented, whichcan control the appearance or functionality of the demonstration app orthe overlay element. The initial settings screen 3100 can include athemes and branding button 3106, which when pressed can cause thecomputing device to load a branding screen 3200.

FIG. 32 is a depiction of a branding screen 3200 displayable on acomputing device according to one embodiment. The branding screen 3200can contain buttons and menus that can be used to make brandingcustomizations and make use of the customizations. The branding screen3200 can have branding menus 3204, each of which can be used to controlthe appearance and functionality of different aspects of the overlayelement. The branding screen 3200 can include a save button 3206, whichwhen pressed can cause the computing device to save the currentsettings, branding customizations, or both as a theme, which can beexported or recalled at a later time. The branding screen 3200 caninclude an email button 3208, which when pressed can cause the computingdevice to generate an email draft containing the settings, brandingcustomizations, or both. The email draft can be generated in the form ofa JSON file. The email draft can be sent using a suitable email app onthe computing device. The branding screen 3200 can include a restorebutton 3210, which when pressed can cause the computing device torestore the settings, branding customizations, or both to defaultsettings. The branding screen 3200 can include a save button 3202, whichwhen pressed can cause the computing device to save any changed brandingcustomizations and return to the app settings screen 2900.

FIG. 33 is a depiction of a demonstration screen 3300 displayable on acomputing device according to one embodiment. The demonstration screen3300 can present a native app representation 3302 along with a live chattab 3304. The native app representation 3302 can be based on theselected graphical representations 2906. The user can switch which ofthe selected graphical representations 2906 is displayed as the nativeapp representation 3302 by providing a suitable input, such as swipingacross the touchscreen of the computing device.

FIG. 34 is a depiction of a demonstration screen 3400 with a functionbar 3406 displayable on a computing device according to one embodiment.Demonstration screen 3400 can display a function bar 3406 upon receivinga specified input from a user, such as after a user swipes across thedemonstration screen 3400. Other specified inputs can be used, such asinput from an accelerometer when the user shakes the computing device.Upon receiving the specified input, the function bar 3406 can appear.The function bar 3406 can contain buttons for using or configuring thedemonstration application itself. The function bar 3406 can include achat button 3410, which when pressed can cause the computing device toopen a chat overlay without the need for the user to press the live chattab 3404, thus bypassing the live chat tab 3404. The function bar 3406can include a purchase button 3412, which when pressed can cause thecomputing device to simulate a purchase made from within the native appdepicted in the native app representation 3402, for the purpose ofdemonstrating functionality of the overlay element (e.g., when theoverlay element is capable of detecting purchases). The function bar3406 can include a call button 3414, which can be used to simulate aphone call being made from the native app depicted in the native apprepresentation 3402, or can be used to initiate a live phone call, suchas to a representative of the company supplying the demonstrationapplication. The function bar 3406 can include a settings button 3408,which when pressed can cause the computing device to load an appsettings screen 2900.

FIG. 35 is a depiction of a demonstration screen 3500 with a pre-chatsurvey window 3502 displayable on a computing device according to oneembodiment. The pre-chat survey window 3502 may be presented over thenative app representation 3508. The native app representation 1904 canbe partially obscured, such as through blurring, fading, or overlaying atranslucent color. The pre-chat survey window 3502 can include a cancelbutton 3504, which when pressed causes the computing device to dismissthe pre-chat survey window 3502. The pre-chat survey window 3502 canfurther include a next button 3506, which when pressed causes thecomputing device to load a name entry window 3600.

FIG. 36 is a depiction of a demonstration screen 3600 with a name entrywindow 3602 displayable on a computing device according to oneembodiment. The name entry window 3602 may be presented over the nativeapp representation 3610. The name entry window 3602 can include a nameentry box 3604 into which a user can type his or her name foridentification purposes during the live chat. A keyboard 3606 can bedisplayed for the purposes of entering characters into the name entrybox 3604. The name entry window 3602 can include a done button 3608,which when pressed can cause the computing device to load a chat overlay3802.

FIG. 37 is a depiction of a demonstration screen 3700 with a chatloading window 3702 displayable on a computing device according to oneembodiment. The chat loading window 3702 can be displayed while the chatoverlay 3802 is loading, which can correspond with the establishment ofa chat connection. The chat loading window 3702 can be presented overthe native app representation 3704.

FIG. 38 is a depiction of a demonstration screen 3800 with a chatoverlay 3802 displayable on a computing device according to oneembodiment. Upon loading the chat overlay 3802, the computing device caneither establish a new chat connection or continue an already existingchat connection. The chat overlay 3802 can enable a user to interactwith an agent through a live chat. The chat overlay 3802 can bepresented over the native app representation 3808. The native apprepresentation 3808 can be obscured as described above. The chat overlay3802 can include a message bubble 3804 including information pertainingto the live chat, sent messages, or received messages. The chat overlay3802 can further include a message box 3806 into which messages may betyped, as well as a send button 3810, which when pressed can cause thecomputing device to transmit any message typed into the message box3806. A keyboard 3812 can be presented to allow a user to entercharacters into the message box 3806.

FIG. 39 is a depiction of a demonstration screen 3900 with a chatoverlay 3902 displayable on a computing device according to oneembodiment. In addition to the various elements described above withreference to demonstration screen 3800, demonstration screen 3900 canfurther include a function panel 3914. The function panel 3914 can beopened (e.g., may appear) in response by a suitable input by a user,such as swiping up on the touchscreen of the computing device from thebottom of the touchscreen. The function panel 3914 can include severalbuttons, each of which may cause the computing device to performadditional functions. Examples of additional functions include theability to take a photo and attach it to the chat, the ability to choosean existing photo on the computing device to attach to the chat, theability to generate an email transcript of the chat, the ability to hidethe chat (e.g., dismiss the chat overlay 3902 without terminating thechat connection), the ability to end the session (e.g., dismiss the chatoverlay 3902 and terminate the chat connection), and the ability to pullup the keyboard again, which may include hiding the function panel 3914.Other functions may be used.

FIG. 40 is a depiction of a demonstration screen 4000 with an alertwindow 4004 displayable on a computing device according to oneembodiment. The overlay element can include an alert window 4004 thatmay be presented to the user for a number of reasons. The alert window4004 can be used to provide diagnostic feedback of the overlay elementto a user of the demonstration application that would normally beaccessible to the user through other means if the overlay element wereintegrated into the live webpage or native app. In FIG. 40, the alertwindow 4004 displays information that a purchase was made. The alertwindow 4004 of FIG. 40 may appear after a user selects the purchasebutton 3412 from FIG. 34. The alert window 4004 can include an acceptbutton 4006, which when pressed can cause the computing device todismiss the alert window 4004. When the alert window 4004 is displayed,the native app representation 4002 can be obscured.

The examples from FIGS. 15 and 26-40 refer to the demonstration of anoverlay element (e.g., a live chat system, including a live chat tab, achat overlay, and other supporting elements) with a graphicalrepresentation of a native app. It will be understood that in place of agraphical representation of a native app, a live native app can bepresented if the operating system running on the computing device soallows. When a live native app is presented with the overlay element,the user can interact with both the live native app and the overlayelement.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments can be practiced without these specific details.For example, circuits can be shown as block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquescan be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove can be done in various ways. For example, these techniques,blocks, steps and means can be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitscan be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that portions of the embodiments can be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartcan describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations can be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in the figure. A process can correspond to a method, afunction, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination corresponds to a return ofthe function to the calling function or the main function.

Furthermore, embodiments can be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks can bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction can represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment can becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. can be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, ticket passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies can beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions can be used in implementing themethodologies described herein. For example, software codes can bestored in a memory. Memory can be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium”, “storage” or“memory” can represent one or more memories for storing data, includingread only memory (ROM), random access memory (RAM), magnetic RAM, corememory, magnetic disk storage mediums, optical storage mediums, flashmemory devices and/or other machine readable mediums for storinginformation. The term “machine-readable medium” includes, but is notlimited to portable or fixed storage devices, optical storage devices,wireless channels, and/or various other storage mediums capable ofstoring that contain or carry instruction(s) and/or data.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed is:
 1. A computer-implemented method, comprising:initiating, at a computing device, a native demonstration application;identifying, at the computing device, a live website associated with oneor more graphical interfaces that include a live overlay element thatincludes a live appearance or a live functionality; loading, via thenative demonstration application, the one or more graphical interfacesof the live website; loading, via the native demonstration application,an interactive demonstration screen that presents a demonstrationoverlay element on the one or more graphical interfaces of the livewebsite, wherein the demonstration overlay element includes ademonstration appearance that corresponds to a live appearance or ademonstration functionality that corresponds to a live functionality onthe one or more graphical interfaces of the live website; receiving, atthe native demonstration application, input corresponding to a selectionof the demonstration overlay element; changing, based on the input, thedemonstration appearance or the demonstration functionality of thedemonstration overlay element on the one or more graphical interfaces ofthe live website; and transmitting the change, wherein when the changeto the live website is received at the live website, the change to thedemonstration appearance or the demonstration functionality of thedemonstration overlay element is incorporated into the correspondinglive appearance or live functionality associated with the live overlayelement associated with the one or more graphical interfaces.
 2. Thecomputer-implemented method of claim 1, wherein the live overlay elementis an interactive chat window.
 3. The computer-implemented method ofclaim 1, further comprising: presenting one or more configurablesettings associated with the demonstration overlay element; andautomatically updating the live overlay element based on the one or moreconfigurable settings, wherein automatically updating the live overlayelement includes changing the live appearance when the demonstrationappearance changes or changing the live functionality when thedemonstration functionality changes.
 4. The computer-implemented methodof claim 1, wherein the live website is usable by one or more mobiledevices.
 5. The computer-implemented method of claim 1, wherein the liveoverlay element is configured to facilitate a communication session. 6.The computer-implemented method of claim 1, wherein partially obscuringthe graphical interface includes blurring or fading the graphicalinterface of the live website.
 7. The computer-implemented method ofclaim 1, further comprising: receiving input corresponding to an action,wherein the action facilitates a display of one or more functions.
 8. Asystem, comprising: one or more data processors; and a non-transitorycomputer-readable storage medium containing instructions which whenexecuted on the one or more data processors, cause the one or moreprocessors to perform operations including: initiating, at a computingdevice, a native demonstration application; identifying, at thecomputing device, a live website associated with one or more graphicalinterfaces that include a live overlay element that includes a liveappearance or a live functionality; loading, via the nativedemonstration application, the one or more graphical interfaces of thelive website; loading, via the native demonstration application, aninteractive demonstration screen that presents a demonstration overlayelement on the one or more graphical interfaces of the live website,wherein the demonstration overlay element includes a demonstrationappearance that corresponds to a live appearance or a demonstrationfunctionality that corresponds to a live functionality on the one ormore graphical interfaces of the live website; receiving, at the nativedemonstration application, input corresponding to a selection of thedemonstration overlay element; changing, based on the input, thedemonstration appearance or the demonstration functionality of thedemonstration overlay element on the one or more graphical interfaces ofthe live web site; and transmitting the change to the live web site,wherein when the change is received at the live website, the change tothe demonstration appearance or the demonstration functionality of thedemonstration overlay element is incorporated into the correspondinglive appearance or live functionality associated with the live overlayelement associated with the one or more graphical interfaces.
 9. Thesystem of claim 8, wherein the live overlay element is an interactivechat window.
 10. The system of claim 8, wherein the instructions furthercause the one or more processors to perform operations including:presenting one or more configurable settings associated with thedemonstration overlay element; and automatically updating the liveoverlay element based on the one or more configurable settings, whereinautomatically updating the live overlay element includes changing thelive appearance when the demonstration appearance changes or changingthe live functionality when the demonstration functionality changes. 11.The system of claim 8, wherein the live website is usable by one or moremobile devices.
 12. The system of claim 8, wherein the live overlayelement is configured to facilitate a communication session.
 13. Thesystem of claim 8, wherein partially obscuring the graphical interfaceincludes blurring or fading the graphical interface of the live website.14. The system of claim 8, further comprising: receiving inputcorresponding to an action, wherein the action facilitates a display ofone or more functions.
 15. A computer-program product tangibly embodiedin a non-transitory machine-readable storage medium, includinginstructions configured to cause a data processing apparatus to:initiate, at a computing device, a native demonstration application;identify, at the computing device, a live website associated with one ormore graphical interfaces that include a live overlay element thatincludes a live appearance or a live functionality; load, via the nativedemonstration application, the one or more graphical interfaces of thelive website; load, via the native demonstration application, aninteractive demonstration screen that presents a demonstration overlayelement on the one or more graphical interfaces of the live website,wherein the demonstration overlay element includes a demonstrationappearance that corresponds to a live appearance or a demonstrationfunctionality that corresponds to a live functionality on the one ormore graphical interfaces of the live website; receive, at the nativedemonstration application, input corresponding to a selection of thedemonstration overlay element; change, based on the input, thedemonstration appearance or the demonstration functionality of thedemonstration overlay element on the one or more graphical interfaces ofthe live website; and transmit the change to the live web site, whereinwhen the change is received at the live website, the change to thedemonstration appearance or the demonstration functionality of thedemonstration overlay element is incorporated into the correspondinglive appearance or live functionality associated with the live overlayelement associated with the one or more graphical interfaces.
 16. Thecomputer-program product of claim 15, wherein the live overlay elementis an interactive chat window.
 17. The computer-program product of claim15, wherein the instructions are further configured to cause the dataprocessing apparatus to: present one or more configurable settingsassociated with the demonstration overlay element; and automaticallyupdate the live overlay element based on the one or more configurablesettings, wherein automatically updating the live overlay elementincludes changing the live appearance when the demonstration appearancechanges or changing the live functionality when the demonstrationfunctionality changes.
 18. The computer-program product of claim 15,wherein the live website is usable by one or more mobile devices. 19.The computer-program product of claim 15, wherein the live overlayelement is configured to facilitate a communication session.
 20. Thecomputer-program product of claim 15, wherein partially obscuring thegraphical interface includes blurring or fading the graphical interfaceof the live website.
 21. The computer-program product of claim 15,wherein the instructions are further configured to cause the dataprocessing apparatus to: receive input corresponding to an action,wherein the action facilitates a display of one or more functions.